Skip to content

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Feb 3, 2025

This PR contains the following updates:

Package Type Update Change
@google-cloud/spanner devDependencies minor 7.17.1 -> 7.18.0
renovate (source) dependencies minor 39.153.1 -> 39.159.0
semver devDependencies patch 7.7.0 -> 7.7.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

googleapis/nodejs-spanner (@​google-cloud/spanner)

v7.18.0

Compare Source

Features
renovatebot/renovate (renovate)

v39.159.0

Compare Source

Features
Miscellaneous Chores

v39.158.2

Compare Source

Bug Fixes
Miscellaneous Chores

v39.158.1

Compare Source

Bug Fixes

v39.158.0

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v39.157.0

Compare Source

Features
Documentation
Miscellaneous Chores

v39.156.2

Compare Source

Build System

v39.156.1

Compare Source

Bug Fixes
  • manager/jsonata: populate extract result with manager config fields (#​33992) (77a5c15)
Documentation
Miscellaneous Chores
  • deps: update containerbase/internal-tools action to v3.5.22 (#​33988) (52ab2d8)
  • deps: update dependency google-github-actions/auth to v2.1.8 (#​33987) (de8140d)

v39.156.0

Compare Source

Features
  • autoreplace: extended logging for autoreplace mismatches (#​33984) (a1c291c)

v39.155.0

Compare Source

Features

v39.154.0

Compare Source

Features

v39.153.2

Compare Source

Miscellaneous Chores
Code Refactoring
Tests
Build System
npm/node-semver (semver)

v7.7.1

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker comp: build renovate managed labels Feb 3, 2025
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Feb 3, 2025
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch 3 times, most recently from 1609fad to 65a35a6 Compare February 3, 2025 21:05
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch 19 times, most recently from 9adab33 to 8573d4e Compare February 4, 2025 16:04
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch from 8573d4e to e6379aa Compare February 4, 2025 17:03
@angular-robot
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package.json
Command failed: yarn update-generated-files
2025/02/04 17:02:03 Downloading https://releases.bazel.build/5.4.0/release/bazel-5.4.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Analyzing: target //ng-dev:npm_package (1 packages loaded, 0 targets configured)
Analyzing: target //ng-dev:npm_package (40 packages loaded, 156 targets configured)
Analyzing: target //ng-dev:npm_package (468 packages loaded, 24969 targets configured)
INFO: Analyzed target //ng-dev:npm_package (473 packages loaded, 25048 targets configured).
INFO: Found 1 target...
[0 / 5] [Prepa] Creating source manifest for @build_bazel_rules_nodejs//internal/pkg_npm:packager
[145 / 219] [Prepa] Compiling TypeScript (devmode) //ng-dev/utils:utils
[150 / 219] Compiling TypeScript (prodmode) //ng-dev/pullapprove:pullapprove; 2s worker ... (4 actions, 3 running)
ERROR: /tmp/renovate/repos/github/angular/dev-infra/ng-dev/perf/workflow/BUILD.bazel:3:11: Compiling TypeScript (prodmode) //ng-dev/perf/workflow:workflow failed: (Exit 1): tsc_wrapped.sh failed: error executing command bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm/@bazel/concatjs/bin/tsc_wrapped.sh @@bazel-out/k8-fastbuild/bin/ng-dev/perf/workflow/workflow_tsconfig.json
ng-dev/perf/workflow/database.ts:9:23 - error TS2307: Cannot find module '@google-cloud/spanner' or its corresponding type declarations.

9 import {Spanner} from '@google-cloud/spanner';
                        ~~~~~~~~~~~~~~~~~~~~~~~

Target //ng-dev:npm_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /tmp/renovate/repos/github/angular/dev-infra/ng-dev/BUILD.bazel:78:8 Assembling npm package ng-dev/npm_package failed: (Exit 1): tsc_wrapped.sh failed: error executing command bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm/@bazel/concatjs/bin/tsc_wrapped.sh @@bazel-out/k8-fastbuild/bin/ng-dev/perf/workflow/workflow_tsconfig.json
INFO: Elapsed time: 41.728s, Critical Path: 11.45s
INFO: 157 processes: 142 internal, 2 local, 1 processwrapper-sandbox, 12 worker.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

File name: .github/ng-renovate/package.json
Command failed: yarn update-generated-files
Loading: 
Loading: 0 packages loaded
Analyzing: target //ng-dev:npm_package (0 packages loaded, 0 targets configured)
INFO: Analyzed target //ng-dev:npm_package (1 packages loaded, 52 targets configured).

INFO: Found 1 target...
[0 / 2] [Prepa] BazelWorkspaceStatusAction stable-status.txt
[150 / 219] Compiling TypeScript (devmode) //ng-dev/ts-circular-dependencies:ts-circular-dependencies; 0s worker ... (4 actions running)
[151 / 219] Compiling TypeScript (prodmode) //ng-dev/auth/login:login; 1s worker ... (4 actions running)
[152 / 219] Compiling TypeScript (prodmode) //ng-dev/auth/login:login; 2s worker ... (4 actions running)
[153 / 219] Compiling TypeScript (prodmode) //ng-dev/auth/login:login; 3s worker ... (4 actions running)
ERROR: /tmp/renovate/repos/github/angular/dev-infra/ng-dev/perf/workflow/BUILD.bazel:3:11: Compiling TypeScript (prodmode) //ng-dev/perf/workflow:workflow failed: (Exit 1): tsc_wrapped.sh failed: error executing command bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm/@bazel/concatjs/bin/tsc_wrapped.sh @@bazel-out/k8-fastbuild/bin/ng-dev/perf/workflow/workflow_tsconfig.json
ng-dev/perf/workflow/database.ts:9:23 - error TS2307: Cannot find module '@google-cloud/spanner' or its corresponding type declarations.

9 import {Spanner} from '@google-cloud/spanner';
                        ~~~~~~~~~~~~~~~~~~~~~~~

Target //ng-dev:npm_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /tmp/renovate/repos/github/angular/dev-infra/ng-dev/BUILD.bazel:78:8 Assembling npm package ng-dev/npm_package failed: (Exit 1): tsc_wrapped.sh failed: error executing command bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm/@bazel/concatjs/bin/tsc_wrapped.sh @@bazel-out/k8-fastbuild/bin/ng-dev/perf/workflow/workflow_tsconfig.json
INFO: Elapsed time: 7.405s, Critical Path: 4.38s
INFO: 8 processes: 5 internal, 3 worker.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

File name: package.json
Command failed: yarn update-generated-files
Loading: 
Loading: 0 packages loaded
Analyzing: target //ng-dev:npm_package (0 packages loaded, 0 targets configured)
INFO: Analyzed target //ng-dev:npm_package (1 packages loaded, 52 targets configured).
INFO: Found 1 target...
[4 / 6] [Prepa] BazelWorkspaceStatusAction stable-status.txt
[153 / 219] Compiling TypeScript (prodmode) //ng-dev/auth/login:login; 0s worker ... (4 actions running)
[154 / 219] Compiling TypeScript (prodmode) //ng-dev/perf/workflow:workflow; 6s worker ... (4 actions, 3 running)
[155 / 219] Compiling TypeScript (prodmode) //ng-dev/perf/workflow:workflow; 8s worker ... (4 actions running)
ERROR: /tmp/renovate/repos/github/angular/dev-infra/ng-dev/perf/workflow/BUILD.bazel:3:11: Compiling TypeScript (prodmode) //ng-dev/perf/workflow:workflow failed: (Exit 1): tsc_wrapped.sh failed: error executing command bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm/@bazel/concatjs/bin/tsc_wrapped.sh @@bazel-out/k8-fastbuild/bin/ng-dev/perf/workflow/workflow_tsconfig.json
ng-dev/perf/workflow/database.ts:9:23 - error TS2307: Cannot find module '@google-cloud/spanner' or its corresponding type declarations.

9 import {Spanner} from '@google-cloud/spanner';
                        ~~~~~~~~~~~~~~~~~~~~~~~

Target //ng-dev:npm_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /tmp/renovate/repos/github/angular/dev-infra/ng-dev/BUILD.bazel:78:8 Assembling npm package ng-dev/npm_package failed: (Exit 1): tsc_wrapped.sh failed: error executing command bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm/@bazel/concatjs/bin/tsc_wrapped.sh @@bazel-out/k8-fastbuild/bin/ng-dev/perf/workflow/workflow_tsconfig.json
INFO: Elapsed time: 11.753s, Critical Path: 9.58s
INFO: 9 processes: 5 internal, 4 worker.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

@josephperrott
Copy link
Member

Closing as this contains a bad release of @google-cloud/spanner which was accidentally released as an empty package.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project comp: build renovate managed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants